Audio-based systems, devices, and methods for domain services

ABSTRACT

A system receives, at a translation device, a first domain name service request. The first domain name service request is from a voice-based communication device receives an audible request. The translation device translates the first domain name service request into a format recognizable by a service provider and then subsequently transmits the translated first domain name service request to the service provider. The service provider may perform a first domain name service in response to the translated first domain name service request to produce first domain name service information. The system may transmit the first domain name service information from the service provider to the translation device, which translates the first domain name service information into a format recognizable by the voice-based communication device and then subsequently transmits the translated first domain name service information to the voice-based communication device.

BACKGROUND

The Domain Name System (“DNS”) is the part of the Internetinfrastructure that translates human-readable domain names into theInternet Protocol (“IP”) numbers needed to establish TCP/IPcommunication over the Internet. DNS allows users to refer to web sites,and other resources, using easier to remember domain names, such as“www.example.com”, rather than the numeric IP addresses associated witha website, e.g., 123.4.56.78, and assigned to computers on the Internet.Each domain name can be made up of a series of character strings (e.g.,labels) separated by dots. The right-most label in a domain name isknown as the top-level domain (“TLD”). Examples of well-known TLDs are“com”; “net”; “org”; and the like. Each TLD supports second-leveldomains, listed immediately to the left of the TLD, e.g., the “example”level in “www.example.com”. Each second-level domain can include anumber of third-level domains located immediately to the left of thesecond-level domain, e.g. the “www” level in www.example.com.

The responsibility for operating each TLD, including maintaining aregistry of the second-level domains within the TLD, can be delegated toa particular organization, known as a domain name registry (“registry”).The registry is primarily responsible for answering queries for IPaddresses associated with domains (“resolving”), typically through DNSservers that maintain such information in large databases, and operatingits top-level domain.

In some instances, in order to obtain a domain name, that domain name isregistered with a registry through a domain name registrar, an entityaccredited by the Internet Corporation for Assigned Names and Numbers(ICANN) and authorized to register Internet domain names on behalf ofend-users.

Currently, to register a domain name, a user must first determinewhether the domain name is available for registration or alreadyregistered (e.g., by another user). To accomplish this, the usermanually performs a search for a web site/service that will allow theuser to search a registry to determine whether the domain name isavailable or already registered. Once the web site/service is located,the user then manually performs the search for the domain name using thewebsite/service. If the domain name is available, the user may manuallyenter the required information and payment to register the domain name.As will be appreciated, each of these steps requires the user tomanually type and view information on a computer or smart device.Accordingly, improved systems and methods for identifying andregistering available domain names that solve the drawbacks and problemsof the current systems and methods would be desirable.

SUMMARY

A system for providing domain name services is disclosed. The systemincludes a processing system including one or more processors. Thesystem also includes a memory system including one or morecomputer-readable media. The one or more computer-readable media containinstructions that, when executed by the processing system, cause theprocessing system to perform operations. The operations includereceiving, at a translation device, a first domain name service requestfrom a voice-based communication device that receives an audiblerequest. The translation device translates the first domain name servicerequest into a format recognizable by a service provider and thensubsequently transmits the translated first domain name service requestto the service provider. The operations also include performing, by theservice provider, a first domain name service in response to thetranslated first domain name service request to produce first domainname service information. The operations also include transmitting thefirst domain name service information from the service provider to thetranslation device, which translates the first domain name serviceinformation into a format recognizable by the voice-based communicationdevice and then subsequently transmits the translated first domain nameservice information to the voice-based communication device.

In another embodiment, the system may include a processing systemincluding one or more processors. The system also includes a memorysystem including one or more computer-readable media. The one or morecomputer-readable media contain instructions that, when executed by theprocessing system, cause the processing system to perform operations.The operations include receiving, at a translation device, aconversation from a voice-based communication device. The translationdevice translates the conversation into a format recognizable by aservice provider and then subsequently transmits the translatedconversation to the service provider. The operations also includeidentifying, by the service provider, a relevant portion of theconversation. The operations also include performing, by the serviceprovider, a domain name service based at least partially upon therelevant portion of the conversation to produce domain name serviceinformation. The operations also include transmitting the domain nameservice information from the service provider to the translation device,which translates the domain name service information into a formatrecognizable by the voice-based communication device and thensubsequently transmits the translated domain name service information tothe voice-based communication device.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate various embodiments of thepresent disclosure and together, with the description, serve to explainthe principles of the present disclosure. In the drawings:

FIG. 1 is a diagram illustrating an example of a system for providingdomain name services, consistent with certain disclosed embodiments;

FIG. 2 is a diagram illustrating an example of a flowchart of a processfor providing domain name services, consistent with certain disclosedembodiments;

FIG. 3 is a diagram illustrating an example of a flowchart of anotherprocess for providing domain name services, consistent with certaindisclosed embodiments;

FIG. 4 is a diagram illustrating an example of a hardware system forperforming at least a portion of one or more of the methods disclosedherein, consistent with certain disclosed embodiments.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.Wherever convenient, the same reference numbers are used in the drawingsand the following description to refer to the same or similar parts.While several examples of embodiments and features of the presentdisclosure are described herein, modifications, adaptations, and otherimplementations are possible, without departing from the spirit andscope of the present disclosure. Accordingly, the following detaileddescription does not limit the present disclosure. Instead, the properscope of the disclosure is defined by the appended claims.

The present disclosure provides for rules-based automation for a processthat was previously done manually. More particularly, the rules-basedautomation described herein may allow a user to submit domain nameservice requests audibly rather than manually (e.g., typing) and toreceive data or information in response to the domain name servicerequests audibly and/or visually (e.g., as text on a screen). Inaddition, the present disclosure adds more to the concept of providingdomain name services than mere computer implementation. For example, thepresent disclosure includes receiving a domain name service request thatis submitted audibly by a user, performing a domain name service inresponse to the domain name service request to produce domain nameservice information, and transmitting the domain name serviceinformation to the user, where the domain name service information ispresented audibly and/or visually to the user. Moreover, the presentdisclosure improves technology in the field of providing domain nameservices.

Technology has been rapidly evolving in the area of voice-basedcommunication and interaction with smart devices. This opens up doorsfor new ways to access, store, and retrieve information. Illustrativevoice-based communication devices may include Amazon's Alexa (Echo/EchoDot) and Google Home. Having the capability of interacting with thesevoice-based communication devices opens new avenues for providing domainname services. Domain name services may be or include providing domainname suggestions, WHOIS data, Registration Data Access Protocol (RDAP),and the like. As used herein “WHOIS data” refers to information relatedto the entity responsible for a particular domain name or IP address.The WHOIS information may include the entity's name, address, emailaddress, phone number, etc. RDAP is a successor to the WHOIS protocoland refers to a computer network communications protocol used to look upinformation related to the entity responsible for a particular domainname or IP address. The RDAP data may be similar to or different fromthe WHOIS data.

FIG. 1 is a diagram illustrating an example of a system 100 forproviding domain name services, consistent with certain disclosedembodiments. The system 100 may include a service registration portal130, a persistent store 140, a translation device 170, and a serviceprovider 180. In general, a customer 110 may communicate with theservice registration portal 130, either directly or via a customerservice representative 120, to subscribe to voice-based services. Usingthe service registration portal 130, the customer 110 (e.g., aregistrar) may subscribe to the voice-based services provided by thesystem 100. After registering, the customer 110 may be assigned a uniqueidentifier for future identification purposes. The identifier may be anapplication programming interface (API) key that is associated with thecustomer's subscription data. This key may be sent by the customer 110to the system 100 when accessing a voice-based communication device 160.This will allow the system 100 to customize the responses sent back tothe voice-based communication device 160 or a device 190 belonging tothe user 150 for consumption. Data describing details of the customer'ssubscription may be stored by the system 100 (e.g., in the persistentstore 140, which may be or include one or more databases).

In various implementations, the key allows the user 150 of the customer110 to request domain name services from the system 100. Moreparticularly, the user 150 may access the voice-based communicationdevice 160 to request the domain name services. In some embodiments, therequest may also include the key. As used herein, “domain name services”may be or include domain name suggestion services (i.e., a service forsuggesting domain names that are available to register), WHOIS services,RDAP services, and the like.

The translation device 170 may translate the request received by thevoice-based communication device 160 into a format recognizable by theservice provider 180, and the service provider 180 may identify and/orprovide data or information that is produced, generated, or output bythe domain name services in response to the request. For example, thevoice-based communication device 160 may receive a voice input from theuser 150. This voice input may be converted into a format specific tothe voice-based communication device 160, for example, a JSON objectwith specific fields. The translation device 170 may convert the JSONformat into a request that is understandable by the service provider180, for example, a REST invocation. The process may be reversed whilereceiving the response. Information corresponding to the key may also belooked-up in the persistent store 140, which may allow the domain nameservices information to be customized for the customer 110 using theinformation in the key. Information corresponding to the key may bestored in the persistent store 140 during the customer registrationprocess. The key may be passed to the service provider 180 from thevoice-based communication device 160 via the translation device 170.Upon receiving the key, the corresponding information may be looked atin persistent store 140 by the service provider 180.

The customized domain name services information may then be transmittedback to the translation device 170, which may translate the customizeddomain name services information into a format recognizable by thevoice-based communication device 160. The voice-based communicationdevice 160 may then audibly transmit, read, or otherwise present thecustomized domain name services information to the user 150 and/orelectronically transmit the customized domain name services informationto a user device 190 (e.g., a computer or smart phone). In someembodiments, the voice-based communication device 160 may alsotransmit/read/audibly present advertisements to the user. Theadvertisements may be provided by the service provider 180 and relatedto the customized domain name services information.

The domain name services information may sometimes include too muchinformation to present to the user 150 at once when the domain nameservices information is read or otherwise audibly presented to the userby the voice-based communication device 160. When this occurs, thedomain name services information may be paginated and cached (e.g., bythe translation device 170). In other embodiments, the domain nameservices information may be persisted, stored, or saved) in the sessiondata between the translation device 170 and the voice-basedcommunication device 160. The translation device 170 may invoke thedomain name services information for the first time or when all thecached information has been presented to the user 150. If more than oneresult is returned by the service provider 180 in response to a domainname service request, the translation device 170 may cache the domainname service responses from the service provider 180 for futurerequests. For example, if 10 results are returned by the serviceprovider 180 in response to a domain name service request, apredetermined number (e.g., two) may be sent back to user 150 at a time.More can be sent in response to further requests. In this case, thetranslation service 170 may query the service provider 180 to retrieveall 10 results and provide a smaller set of results to the user 150 at atime until all the results in the cache are exhausted before queryingthe service provider 180.

In some embodiments, interfaces and/or APIs may be provided from/by theservice provider 180 that may be processed, interacted with, orcommunicated with directly by the voice-based communication device 160.This may allow the translation device 170 to be bypassed or omittedaltogether.

FIG. 2 is a diagram illustrating an example of a flowchart of a process200 for providing domain name services, consistent with certaindisclosed embodiments. In various implementations, the process 200 maybe performed by the system 100, as shown in FIG. 1. The process 200 ispresented from the perspective of the system 100 (i.e., not the customer110 or the user 150).

The process 200 begins at operation or stage 205 with receiving a firstdomain name service request that was submitted audibly by the user 150.For example, the user 150 may audibly ask the voice-based communicationdevice 160 for domain name services (e.g., related to football). Therequested domain name services may be or include domain name suggestionsrelated to a subject in general (e.g., football) or related to aparticular domain name (e.g., www.football.com). In another example, therequested domain name services may be or include looking up or findingWHOIS data and/or RDAP data related to the subject in general or theparticular domain name. In another example, the requested domain nameservices may be looking up or finding information related to part of, orrelated to, a particular TLD (e.g., net). In yet another example, therequested domain name services may be looking up or finding informationin another language (e.g., related to football, but in Spanish).

The voice-based communication device 160 may receive and interpret thefirst request and then transmit the first request to the translationdevice 170. The translation device 170 may translate the first requestinto a format recognizable by the service provider 180. For example, tobe able to integrate or interface with a name suggestion REST API,Amazon's Alexa Lambda functions may be used, or an intermediatetranslation gateway may be used, to act as a bridge. The translatedfirst request may then be transmitted to the service provider 180.

The process 200 may then include identifying or performing domain nameservices in response to the (e.g., translated) first request, as atstage 210. Stage 210 may be performed by the system 100 (e.g., by thepersistent store 140 and/or the service provider 180). The domain nameservices may be identified by the interaction from the user 150 (userrequest). For example, the request may be to check the available domainnames, to know who owns an already registered domain, or to register anavailable domain. The translation device 170 may have a mapping fordomain name service (e.g., REST endpoint) to forward the request basedon the user request. For example, the domain name services maydetermine, identify, or indicate that a particular domain name (e.g.,football.com) is already registered by a particular entity. The domainname services may also determine, identify, or indicate WHOIS dataand/or RDAP data related to the particular entity (e.g., the name,address, email address, phone number, etc.). The domain name servicesmay also or instead determine or provide domain name suggestions relatedto football that are available for registration, such asbest-football.com, the-football.net, and football-us.com. If therequested domain name services are part of, operate on, or are relatedto a particular TLD (e.g., net), the domain name services may includedetermining, identifying, or providing domain name suggestions havingthat TLD, such as best-football.net, the-football.net, andfootball-us.net. If the requested domain name services include languagefiltering (e.g., Spanish filtering), the determined or identified domainname suggestions may be at least partially in that language, such astufootball.com, casafootball.net, and footballverde.com.

The process 200 may then include transmitting information or data thatwas produced, generated, or output by the domain name services to theuser 150 in response to the first request, as at stage 215. This mayinclude transmitting the information output by the domain name servicesfrom the service provider 180 to the translation device 170. Thetranslation device 170 may translate the domain name servicesinformation into a format recognizable by the voice-based communicationdevice 160. The translation device 170 may then transmit the (e.g.,translated) domain name services information to the voice-basedcommunication device 160, which may audibly read or present the domainname services information to the user 150. Instead of, or in additionto, audibly reading the domain name services information to the user150, the voice-based communication device 160 may transmit the domainname services information to the user's device 190. The voice-basedcommunication device 160 may then ask the user 150 whether the user 150would like additional domain name services (e.g., additional domain namesuggestions).

The process 200 may then include receiving a second request foradditional domain name services (e.g., additional domain namesuggestions) that was submitted audibly by the user 150, as at stage220. The process 200 may then include identifying or performingadditional domain name services in response to the second request, as atstage 225. The process 200 may then include transmitting information ordata that was produced, generated, or output by the additional domainname services to the user 150, as at stage 230. Stages 220, 225, and 230may be similar to stages 205, 210, and 215, respectively, and are notrepeated again in detail. The additional domain name suggestions mayinclude, for example, floris-football.com and school-football.com.

The process may then include receiving a third request for additionaldomain name services (e.g., to register a domain name) that wassubmitted audibly by the user 150, as at stage 235. The domain name maybe one of the domain names included in the domain name suggestionsinformation provided by the system (e.g., at stage 215 or 230). Forexample, the user 150 may audibly request to register the domain namebest-football.net. The third request may be transmitted to the system100 in the same manner described above (e.g., at stage 205).

The process 200 may then include identifying information needed from theuser 150 to register the domain name in response to the third request,as at stage 240. For example, the voice-based communication device 160may provide a way to register/link the customer information so that itcan be used for certain domain name services (e.g., registering adomain). This information can also be collected from the user 150 at thetime of invoking such service via voice prompts or through linked smartdevice 190. Stage 240 may be performed by the system 100 (e.g., by thepersistent store 140 and/or the service provider 180). The informationmay include name, address, email address, payment information, etc.

The process 200 may then include transmitting a request for theregistration information to the user 150, as at stage 245. The requestmay be transmitted to the user 150 in the same manner described above(e.g., at stage 215).

The process 200 may then include receiving the registration informationfrom the user 150 in response to the request, as at 250. The user 150may audibly submit the registration information (e.g., by speaking theregistration information to the voice-based communication device, asdescribed above), or the user 150 may submit the information using thedevice 190 (e.g., by typing the registration information).

The process 200 may then include registering the domain name for theuser 150 using the registration information provided by the user, as at255. The domain name may be registered by the system 100 (e.g., by theservice provider 180), as is known in the DNS art.

The process 200 may then include transmitting a message and/or otherinformation to the user 150 to indicate that the domain name has beenregistered, as at 260, which completes the process 200.

In embodiments that include a key as part of the first domain nameservice request at 205, the key may be used to look up or otherwiseidentify (e.g., in the persistent store 140) customized informationrelated to or associated with the key. The customized information may beor include information related to the customer (e.g., the registrar) 110to which the key was assigned. This may allow the domain name servicesinformation or the final message to be customized for the particularcustomer 110. For example, the conclusion message may be customized tothank the user 150 for using the particular customer 110.

Instead of, or in addition to, using the key to customize the domainname services information and/or the message, the first request (e.g.,at stage 205) by the user 150 may request the domain name services froma particular customer (e.g., registrar) 110. This may also allow thedomain name services and/or the message to be customized for theparticular customer 110 and the customer's users 150.

As mentioned above, in some embodiments, the system 100 may transmitadvertisements (advertising information) related to the domain nameservices information. For example, if the first request is related topizza (e.g., a request for domain name suggestions related to pizza),the domain name services information and/or the message transmitted bythe system 100 may include an advertisement or advertising information,such as “Buy a large 2-topping pizza at AAA Pizzeria for $5.99.” Theadvertisement may be read or otherwise presented audibly to the user 150by the voice-based communication device 160 and/or transmitted to theuser's device 190 (e.g., via SMS, email, or other push notifications)for display or audible announcement by the device 190.

In some implementations, the system 100 may have additionalfunctionality to charge the advertiser per advertisement. In addition,by having a pricing model for the customized domain name servicesinformation, revenue can be generated using a pay-per-use model orrecurring subscription fees. API responses may also contain relatedadvertisements paid for by interested parties. And, anonymized userinterest data may be sold to other companies.

FIG. 3 is a diagram illustrating an example of a flowchart of anotherprocess 300 for providing domain name services, consistent with certaindisclosed embodiments. In various implementations, the process 300 maybe performed by the system 100, as shown in FIG. 1. The process 300 ispresented from the perspective of the system 100 (i.e., not the customer110 or the user 150).

The process 300 begins at operation or stage 305 with receiving aconversation that was submitted audibly by the user 150. In thisexample, the user 150 may be or include a domainer (as used herein“domainer” refers to a domain investor), a registrar, a domain namereseller, or the like. The user 150 may turn on the voice-basedcommunication device 160 such that the voice-based communication device160 is configured to listen to and/or record conversations (e.g., by theuser 150). In at least one embodiment, the user 150 may set thevoice-based communication device 160 into a “name suggestion” mode. Atleast a portion of the conversations may be related to technicalservices, solutions, and/or products provided by the user 150; however,at least a portion of the conversations may be unrelated to thetechnical services, solutions, and/or products provided by the user 150.

The voice-based communication device 160 may listen to and/or record theconversations over an extended period of time (e.g., hours, days, weeks,etc.). The conversations may be listened to and/or recorded duringmeetings specifically discussing the technical services, solutions,and/or products provided by the user 150, or the conversations may belistened to and/or recorded during the entirety of working hours (e.g.,from 8 AM 6 PM).

The voice-based communication device 160 may periodically (e.g., at theend of a meeting, at the end of each day, at the end of each week, etc.)transmit the conversations to the translation device 170 and/or theservice provider 180. In another example, the voice-based communicationdevice 160 may transmit the conversations when instructed to do so bythe user 150. The voice-based communication device 160 may transmit theconversations to the translation device 170. The translation device 170may translate the conversations into a format recognizable by theservice provider 180. The translated conversations may then betransmitted to the service provider 180.

The process 300 may then include identifying relevant portions of theconversations (e.g., from the conversations as a whole), as at stage310. Stage 310 may be performed by the system 100 (e.g., by thepersistent store 140 and/or the service provider 180). The relevantportions of the conversations may include those portions related to theuser's technical services, solutions, and/or products. The relevantportions of the conversations may be identified by generating a list ofthe words in the conversations that are repeated most frequently. Inother embodiments, the relevant portions of the conversations may beidentified by utilizing the dictionary (e.g., tokenization), or by notutilizing the dictionary (e.g., one-character tokenization). In yetother embodiments, the relevant portions of the conversations may beidentified by breaking the sentences down (e.g., via tokenization) andzone file mapping to identify what relevant domain names have beenregistered. In yet another embodiment, the sentences may be mapped tovectors that can be decoded to produce domain names. In yet anotherembodiment, keywords may be extracted from the sentences and run throughan algorithm.

The process 300 may then include employing or executing domain nameservices using, at least partially, the relevant portions of theconversation, as at stage 315. In at least one embodiment, the domainname services may determine, identify, or output domain name suggestionsthat are based at least partially upon the relevant portions of theconversation. For example, the domain name services may determine,identify, or output one or more domain name suggestions (e.g., foravailable/unregistered domain names) that are related to the user'stechnical services, solutions, and/or products, where the suggestionsare determined based at least partially upon one or more words that werefrequently repeated in the conversation received in stage 305.

Identifying or determining the domain name suggestions from a user'sspeech may leverage deep neural networks. More particularly, this mayinclude sequence-to-sequence models, consisting of two neural networks,an encoder which processes the speech, and a decoder which generatesdomain names. The encoder may be a long short-term memory (LSTM) neuralnetwork reading the words in the textual transcription of the speech andencoding them into a fixed-length vector. A neural attention mechanismmay be used to learn to better focus on relevant parts of theconversation. The decoder may be a character-based LSTM recurrent neuralnetwork that decodes the thought vectors to domain name suggestions.With such architecture, it may be possible to generate domain namesuggestions from textual data (e.g., speech transcription in this case).

In another embodiment, identifying or determining the domain namesuggestions may include identifying, by a processor in the serviceprovider 180, a subset of registered domain names having at least onespecified characteristic. For example, the service provider 180 mayconsider the characteristics and prioritize based on a consolidatedranking. This can be altered by the user 150 by requesting a specificcharacteristic in the request with specific instructions (e.g., “I'minterested in location specific domains,” or “I'm interested inavailable domains which are receiving traffic already or domains thatwere registered earlier but are available now.”). The system 100 canalso extract the context based on the conversation. For example, a realestate company in Virginia may want a localized domain name (e.g.,RealEstateVA.com). The at least one specified characteristic may be orinclude at least one of: a registration history characteristic, alinguistic characteristic, a traffic characteristic, a WHOIS informationcharacteristic, a content characteristic, a geographical characteristic,a routing characteristic, an aftermarket pricing characteristic, a TLDcharacteristic, or a security characteristic.

Domain name suggestion may provide the ability to receive geo-basedsuggestions, affix-based suggestions, and/or spinner-based suggestions.This may be leveraged by extracting keywords/named entities from thespeech (e.g., any keyword extraction/NER technique may be used), andusing these keywords with existing algorithms. For example, relevantkeywords may be extracted from speech, such as “movie” and “cinema,” andnamed entities may also be extracted, such as “Andrew” and “New York.”Existing name suggestion services may be queried with these words toobtain particular types of suggestions according to user preferences(e.g., affixes, geo, nicknames, etc.). For example, affix-basedsuggestions may include “ActionMovie.com,” “MovieTheatre.com,” and“MovieFestivalOnline.com,” and geo-based suggestions may include“AmericanCinema.com” and “NY-Movie.com.”

In another embodiment, the domain name services may be or includeservices that find or identify and return WHOIS data and/or RDAP datathat contains or is otherwise related to words or information that arein the relevant portions of the conversation, from stage 310. Forexample, the domain name services may find WHOIS data and/or RDAP data(e.g., from a WHOIS and/or RDAP database) for one or more domain namesthat are already registered and that are related to the user's technicalservices, solutions, and/or products, where the relationship isdetermined based at least partially upon one or more words that arefrequently repeated in the conversation. For example, the service mayidentify and return certain WHOIS data because it contains one or morewords that are frequently repeated in the conversation.

In at least one embodiment, the conversation received at stage 305 mayalso include geographic data related to the location of the user 150,and the domain name services may return outputs that are based at leastpartially upon the location of the user. In another embodiment, thedomain name services may include a service that generates or determinesa ranking or score (e.g., 95 out of 100) that indicates how similar theoutputted domain name services information is to the relevant portionsof the conversation.

The process 300 may then include transmitting, to the user 150,information or data that was produced, generated, or output by thedomain name service, as at stage 320. The domain name servicesinformation may be identified, generated, or otherwise determined andtransmitted periodically (e.g., once per day, once per week, etc.), andmay be based upon the conversations that are received by the system 100during that time period. Transmitting the domain name servicesinformation may include transmitting the domain name servicesinformation from the service provider 180 to the translation device 170.The translation device 170 may translate the domain name servicesinformation into a format recognizable by the voice-based communicationdevice 160 in the same manner as described above. The translation device170 may then transmit the (e.g., translated) domain name servicesinformation to the voice-based communication device 160, which mayaudibly read or otherwise audibly present the domain name servicesinformation to the user 150. Instead of, or in addition to, audiblyreading the domain name services information to the user 150, thevoice-based communication device 160 may transmit the domain nameservices to the user's device 190 for display or audio presentation.

The process 300 may then include receiving instructions to adjustsettings of the domain name service(s) at the service provider 180 afterthe domain name services information is transmitted to the user 150, asat stage 325. The process 300 may then include adjusting the settings inresponse to the instructions, as at stage 330. In various embodiments,adjusting the settings may include identifying one or more words in theconversations and/or the domain name services information (e.g., thedomain name suggestions) that are unrelated to the user's technicalservices, solutions, and/or products, such that the information outputby the domain name service is not based on the identified, unrelatedwords. For example, natural language processing, machine (deep)learning, and other artificial intelligence and text processing methodscan be utilized to extract the relevant content from the conversation.In various embodiments, adjusting the settings may include adjusting afrequency at which the domain name services are executed and at whichthe domain name services information is transmitted to the user 150(e.g., once per day, once per week, etc.). The frequency may be providedby the service provider 180, but the frequency may be changed by theuser 150.

FIG. 4 is a diagram illustrating an example of a hardware system 400 forperforming at least a portion of one or more of the methods 200, 300disclosed herein, consistent with certain disclosed embodiments. Theexample of a hardware system 400 includes examples of system componentsthat may be used. The components and arrangement, however, may bevaried.

As the example of FIG. 4 shows, the hardware system 400 may include acomputer 401. The computer 401 may include a processor 410, a memory420, a storage 430, and input/output (I/O) devices (not pictured). Thecomputer 401 may be implemented in various ways and can be configured toperform any of the embodiments described above. In some embodiments, thecomputer 401 can be a general-purpose computer such as, for example, adesktop computer, a laptop, a tablet device, a mobile device (e.g., asmartphone), etc. In other embodiments, the computer 401 can be a morecapable computing device such as, for example, a data base server (e.g.,a domain name registry), a web server, a mainframe computer, etc. Thecomputer 401 may be standalone or may be part of a subsystem, which may,in turn, be part of a larger system. For example, the computer 401 canbe at least a portion of the system 100 (e.g., the persistent store 140,the translation device 170, and/or the service provider 180).

The processor 410 may include one or more known processing devices, suchas a microprocessor from the Intel Core™ family manufactured by Intel™,the Phenom™ family manufactured by AMD™, or the like. The memory 420 mayinclude one or more storage devices configured to store informationand/or instructions used or executed by the processor 410 to performcertain functions and operations related to the disclosed embodiments.The storage 430 may include a volatile or non-volatile, magnetic,semiconductor, tape, optical, removable, non-removable, or other type ofcomputer-readable medium used as a storage device. In some embodiments,the storage 430 can include or contain, for example, the data receivedby the persistent store 140. [53] In an embodiment, the memory 420 mayinclude one or more programs or subprograms including instructions thatmay be loaded from the storage 430 or elsewhere that, when executed bythe processor 410 of the computer 401, perform various procedures,operations, stages, or processes consistent with disclosed embodiments.For example, the memory 420 may include a domain name services program425 for performing at least a portion of the method 200, and/or themethod 300. The memory 420 may also include other programs that performother functions, operations, and processes, such as programs thatprovide communication support, Internet access, etc. The domain nameservices program 425 may be embodied as a single program, oralternatively, may include multiple sub-programs that, when executed,operate together to perform the function of the domain name servicesprogram 425 according to disclosed embodiments.

The computer 401 may communicate over a link with a network 440 to, forexample, a DNS registry, a DNS registrar, a voice-based communicationdevice 160, etc. For example, the link may be a direct communicationlink, a local area network (LAN), a wide area network (WAN), or othersuitable connection. The network 440 may include the internet, as wellas other networks, which may be connected to various systems anddevices.

The computer 401 may include one or more input/output (I/O) devices (notpictured) that allow data (information) to be received and/ortransmitted by the computer 401. The I/O devices may also include one ormore digital and/or analog communication I/O devices that allow thecomputer 401 to communicate with other machines and devices. The I/Odevices may also include input devices such as a keyboard or a mouse,and may include output devices such as a display or a printer. Thecomputer 401 may receive data (e.g., domain name service requests,registration information, conversations, etc.) from external machinesand devices and output data (e.g., domain name services information) toexternal machines and devices via I/O devices. The configuration andnumber of input and/or output devices incorporated in I/O devices mayvary as appropriate for various embodiments. Example uses of thehardware system 400 can be described by way of example with reference tothe embodiments described above.

While the teachings have been described with reference to the exampleembodiments, those skilled in the art will be able to make variousmodifications to the described embodiments without departing from thetrue spirit and scope. The terms and descriptions used herein are setforth by way of illustration only and are not meant as limitations. Inparticular, although the method has been described by examples, thesteps of the method may be performed in a different order thanillustrated or simultaneously. Furthermore, to the extent that the terms“including”, “includes”, “having”, “has”, “with”, or variants thereofare used in either the detailed description and the claims, such termsare intended to be inclusive in a manner similar to the term“comprising.” As used herein, the term “one or more of” with respect toa listing of items such as, for example, A and B, means A alone, Balone, or A and B. Those skilled in the art will recognize that theseand other variations are possible within the spirit and scope as definedin the following claims and their equivalents.

What is claimed is:
 1. A system for providing domain name services, thesystem comprising: a processing system comprising one or more processorsfor a translation device; and a memory system comprising one or morecomputer-readable media, wherein the one or more computer-readable mediacontain instructions that, when executed by the processing system, causethe processing system to perform operations comprising: receiving, atthe translation device, a first request in a first format from avoice-based communication device that receives the first request,wherein the first request comprises an audible request; determining,based on the first request, the first request is for a first domain nameservice, wherein the translation device is configured to translate thefirst request into a second format recognizable by a domain name serviceprovider of the first domain name service, wherein the first domain nameservice comprises a service related to domain name registration andavailability information, and wherein the translation device isconfigured to transmit the translated first request to the domain nameservice provider; receiving, from the domain name service provider, afirst domain name service information that was produced by the firstdomain name service in response to the translated first request, whereinthe translation device is configured to translate the first domain nameservice information into the first format recognizable by thevoice-based communication device; transmitting the translated firstdomain name service information to the voice-based communication device;receiving, at the translation device, a second request in the firstformat from the voice-based communication device that receives thesecond request; and determining, based on the second request, the secondrequest is for a second domain name service, wherein the translationdevice is configured to translate the second request into the secondformat recognizable by a second domain name service provider of thesecond domain name service, and wherein the translation device isconfigured to transmit the translated second request to the seconddomain name service provider.
 2. The system of claim 1, wherein thefirst request is limited to a top level domain.
 3. The system of claim1, wherein the first request is for WHOIS data related to a domain name.4. The system of claim 3, wherein the first domain name serviceinformation comprises an advertisement related to the domain name. 5.The system of claim 1, wherein the first request is for suggestions foravailable domain names that are related to a subject.
 6. The system ofclaim 5, wherein the second request is for registering a domain name ofthe available domain names in response to the translated first domainname service information.
 7. The system of claim 6, wherein theoperations further comprise: receiving, at the translation device, arequest for registration information from the domain name serviceprovider, wherein the translation device translates the request forregistration information into the first format recognizable by thevoice-based communication device, wherein the translation devicesubsequently transmits the translated request for registrationinformation to the voice-based communication device; and receiving, atthe translation device, the registration information from thevoice-based communication device in response to the translated requestfor registration information, wherein the translation device translatesthe registration information into the second format recognizable by thedomain name service provider, wherein the translation devicesubsequently transmits the translated registration information to thedomain name service provider.
 8. The system of claim 1, wherein thefirst request comprises a key that identifies a registrar, and whereinthe first domain name service information is customized based at leastpartially upon information related to the key.
 9. The system of claim 1,wherein the translated first domain name service information ispaginated and cached by the translation device after a predeterminedamount of time for the voice-based communications device to audiblypresent the translated first domain name service information to a user.10. The system of claim 1, wherein the translated first domain nameservice information is also transmitted to a device of a user after apredetermined amount of time for the voice-based communications deviceto audibly present the translated first domain name service to a user.11. The system of claim 1, wherein the first format comprises a JSONformat, and wherein the second format comprises a representational statetransfer format.
 12. The system of claim 1, wherein the first domainname service information comprises domain name suggestion, domain nameregistration, and/or domain name availability information.
 13. Thesystem of claim 1, wherein the service related to domain nameregistration and availability information comprises a domain namesuggestion service.
 14. A system for providing domain name services, thesystem comprising: a processing system comprising one or moreprocessors; and a memory system comprising one or more computer-readablemedia, wherein the one or more computer-readable media containinstructions that, when executed by the processing system, cause theprocessing system to perform operations comprising: receiving, at atranslation device, a conversation from a voice-based communicationdevice in a first format; determining, based on the conversation, theconversation comprises a first request for a first domain name service,wherein the translation device is configured to translate theconversation into a second format recognizable by a domain name serviceprovider of the first domain name service, wherein the first domain nameservice comprises a service related to domain name registration andavailability information, and wherein the translation device isconfigured to transmit the translated conversation to the domain nameservice provider; identifying, by the domain name service provider, arelevant portion of the conversation; performing, by the domain nameservice provider, a first domain name service based at least partiallyupon the relevant portion of the conversation to produce a first domainname service information; transmitting the first domain name serviceinformation from the domain name service provider to the translationdevice, wherein the translation device is configured to translate thefirst domain name service information into the first format recognizableby the voice-based communication device; and transmitting the translatedfirst domain name service information to the voice-based communicationdevice; and determining, based on the conversation, the conversationcomprises a second request for a second domain name service, wherein thetranslation device is configured to translate the conversation into thesecond format recognizable by a second domain name service provider ofthe second domain name service, and wherein the translation device isconfigured to transmit the translated conversation to the second domainname service provider.
 15. The system of claim 14, wherein theconversation is recorded over a period of days.
 16. The system of claim14, wherein the relevant portion of the conversation is related totechnical services, solutions, or products provided by a user.
 17. Thesystem of claim 16, wherein the first domain name service informationcomprises WHOIS data based upon the relevant portion of theconversation.
 18. The system of claim 16, wherein the first domain nameservice information comprises one or more domain name suggestions basedupon the relevant portion of the conversation.
 19. The system of claim18, wherein the first domain name service information comprises aplurality of domain name suggestions, and further comprising generatinga score for each of the domain name suggestions corresponding to howsimilar each of the domain name suggestions is to the relevant portionof the conversation.
 20. The system of claim 18, wherein receiving theconversation comprises receiving a plurality of conversationsperiodically, and wherein the first domain name service is updated inresponse to receiving new ones of the plurality of conversations. 21.The system of claim 20, wherein the operations further compriseadjusting a setting after the translated first domain name serviceinformation is transmitted.
 22. The system of claim 21, whereinadjusting the setting comprises identifying one or more words in theconversation that are not relevant.
 23. The system of claim 21, whereinadjusting the setting comprises adjusting a frequency at which the firstdomain name service information is transmitted after the domain nameservice is updated.